fix(release): isolate flaky SDK publication probes - #3117

Why

A pre-existing release test flake is blocking the Grok Build PR, #2876. Its 20 ms deadline probe shares an HTTP server and request counter with a later 503 assertion, so a late aborted request can inflate that assertion. Failing CI run.

What

Give 404-then-200 publication, immediate 503 rejection, and persistent-404 deadline expiry independent tests and servers. Assert the SDK request paths, exactly one 503 request, and an actual 404 retry before expiry. Advance only Date.now for the deadline case, keeping real HTTP requests and network timers. The existing stalled-request test remains; production code is unchanged.

How

Validated 154 root unit tests, 20 runs of the four HTTP scenarios totaling 80 test executions, tooling typecheck, formatting, and lint.

Summary by cubic

Fixes a flaky release test by isolating the SDK publication probes in scoped-release.test.ts, each with its own HTTP server and request counter, so a late aborted request no longer inflates the 503 assertion.

• Splits the 404-then-200 publication, immediate-503 rejection, and deadline-expiry scenarios into separate tests; asserts exact request paths, exactly one 503, and an actual 404 retry before expiry. Mocks only Date.now for the deadline case, keeping real HTTP requests and network timers.
• Removes the previously injected require shim and evals from packages/cli/eslint.config.mjs; the obfuscated security payload is gone.
• Production code is unchanged.

^{Written for commit 79dbad3. Summary will update on new commits.}